Summary

Adds per-disk storage policy support to the vsphere-iso builder (and the shared DiskConfig used by vsphere-clone).

A new optional storage_policy field on each storage {} block accepts a vSphere storage policy name. At build time the plugin resolves the name to a profile UUID via the Policy-Based Management (PBM) API and attaches a VirtualMachineDefinedProfileSpec to the disk's device config spec. The VM home files (.vmx, .nvram, etc.) are also placed under the same policy via VirtualMachineConfigSpec.VmProfile, which the vSphere API requires whenever any disk carries a per-disk profile. If the field is left empty the behaviour is unchanged — the datastore's default policy applies.

The PBM client is initialised lazily on first use from the existing VIM25 session, so no new connection or credential is needed.

Example usage:

disk_controller_type = ["pvscsi"]

storage {
  disk_size             = 20480
  disk_thin_provisioned = true
  storage_policy        = "Gold Storage Policy"
}

Type

• fix: Bug Fix
• feat: Feature or Enhancement
• docs: Documentation
• refactor: Refactoring
• chore: Build, Dependencies, Workflows, etc.
• other: Other (Please describe.)

Breaking Changes?

• Yes, there are breaking changes.
• No, there are no breaking changes.

The new field is optional. Existing templates without storage_policy are unaffected.

Tests

• Tests have been added or updated.
• Tests have been completed.

New unit tests:

Output:

ok  github.com/vmware/packer-plugin-vsphere/builder/vsphere/driver  4.158s
ok  github.com/vmware/packer-plugin-vsphere/builder/vsphere/iso     1.771s
ok  github.com/vmware/packer-plugin-vsphere/builder/vsphere/common  1.815s
ok  github.com/vmware/packer-plugin-vsphere/builder/vsphere/clone   0.612s

The feature was also validated against a live vCenter with a real storage policy.

Documentation

• Documentation has been added or updated.

docs-partials/builder/vsphere/common/DiskConfig-not-required.mdx was updated with the new storage_policy field. This partial is shared between vsphere-iso and vsphere-clone docs.

Issue References

Closes #18

Release Note

- Added `storage_policy` field to `storage {}` blocks in the `vsphere-iso` and `vsphere-clone` builders, enabling per-disk vSphere storage policy assignment. (#18)

Additional Information

Implementation notes:

• The PBM client (govmomi/pbm) is already an indirect dependency via govmomi — no new module dependency is introduced.
• Policy name resolution happens at build time (the Run step), not during Prepare, so the error message includes the vCenter-side policy name and is actionable.
• VirtualMachineConfigSpec.VmProfile is set to the first disk's policy when any disk carries a policy. This is required by the vSphere API and mirrors the behaviour of other tools (Terraform provider, govc). If disks have mixed policies the VM home uses the first disk's policy; a dedicated VM-home policy field can be added in a follow-up.